Dependency graph

Changed files are highlighted in green.

flowchart LR

subgraph 0["src"]
subgraph 1["expo"]
2["index.ts"]
end
subgraph 3["lib"]
subgraph 4["db"]
5["manager.ts"]
6["schema.ts"]
subgraph 7["phone_call"]
8["models.ts"]
9["index.ts"]
A["operations.ts"]
B["types.ts"]
end
end
end
subgraph C["react"]
D["index.ts"]
E["useDatabaseManager.ts"]
end
subgraph F["server"]
G["index.ts"]
H["storage.ts"]
end
end
2-->5
2-->5
2-->6
5-->6
6-->8
9-->8
9-->A
9-->B
A-->8
A-->B
D-->5
D-->5
D-->9
D-->6
D-->E
E-->5
G-->5
G-->5
G-->6
G-->H
H-->5

style 6 fill:lime,color:black
style 8 fill:lime,color:black
style 9 fill:lime,color:black
style A fill:lime,color:black
style B fill:lime,color:black
style D fill:lime,color:black

Coverage Report

API Changes

@anuma/sdk/expo

✏️ Modified

- SDK_SCHEMA_VERSION = 19
+ SDK_SCHEMA_VERSION = 20

@anuma/sdk/react

🆕 Added
createPhoneCallOp (function) · CreatePhoneCallOptions (interface) · deletePhoneCallsByConversationOp (function) · getPhoneCallByOfferOp (function) · getPhoneCallsByConversationOp (function) · PhoneCall (class) · PhoneCallOperationsContext (interface) · PhoneCallStatus (type) · phoneCallToStored (function) · StoredPhoneCall (interface) · updatePhoneCallOp (function) · UpdatePhoneCallOptions (interface)

✏️ Modified

- SDK_SCHEMA_VERSION = 19
+ SDK_SCHEMA_VERSION = 20

Integration Check ✅

Thanks for the thorough review Pasumarthi Rutwik (@rutwik2001)! Here's the breakdown:

1. created_at/updated_at not set on create — WatermelonDB auto-populates these. The Project model follows the same pattern (never sets them in _setRaw) and works correctly.

2. updated_at not bumped on update — WatermelonDB's record.update() automatically bumps updated_at.

3. Unsafe cast record.status as PhoneCallStatus — Matches the existing pattern across all SDK models. Not worth special-casing one table.

4. Schema isOptional vs @text mismatch — Minor inconsistency but not broken since we always write "". Low priority cleanup.

5. No delete operation — Good catch. Added deletePhoneCallsByConversationOp in 79a4114 — hard-deletes all phone call records for a conversation to prevent unbounded growth.

6. getPhoneCallByOfferOp silently picks first — offerMessageId is a WatermelonDB unique message ID so duplicates can't occur in practice.

Schema version collision (blocking) — The branch HEAD is still 79a41147 from April and hasn't been rebased. Main is now at SDK_SCHEMA_VERSION = 27 and v20 is already taken by the memory_vault.updated_at index migration. Six more migrations have landed since (v21 embedding, v22 is_system, v23 conversation_summaries, v24 folder context, v25 saved_tools, v26 app_files, v27 tool_call_events). As-is, merging this would either silently overwrite the v20 migration step or fail outright. We need to rebase, bump to v28, update the version comment block in schema.ts, and add the phone_calls migration after the v27 step.

src/lib/db/schema.ts — getPhoneCallsByConversationOp sorts by created_at after filtering by conversation_id, so without an index WatermelonDB will full-scan all rows matching the conversation and sort in memory. Sibling tables that sort by created_at all index it (media, app_files, saved_tools, vault_folders). Lets add isIndexed: true on created_at in both the table schema and the migration.

src/lib/db/phone_call/models.ts — Every other table with a conversation_id FK declares a belongs_to association (see media/models.ts, appFiles/models.ts, and the inverse has_many on Conversation). Without it, code that wants to relate phone calls back to a conversation has to query manually and WatermelonDB can't validate the FK direction. Lets add the association and consider the inverse has_many on Conversation if call-from-conversation traversal is expected.

src/lib/db/phone_call/operations.ts:38-47 — createPhoneCallOp doesn't write created_at / updated_at explicitly and relies on WatermelonDB's decorator auto-population. Sibling ops (savedTools/operations.ts, appFiles/operations.ts) set both timestamps explicitly inside the create callback so behavior isn't decorator-dependent. Lets match that pattern, and bump updated_at explicitly inside updatePhoneCallOp too.

src/lib/db/phone_call/models.ts:13 — Sibling models (savedTools/models.ts:22, appFiles/models.ts:13) use @readonly @date('created_at') to prevent accidental rewrites of the creation timestamp. The plain @date here lets callers mutate createdAt via _setRaw which is almost certainly not the intent. Lets add @readonly.

src/lib/db/phone_call/models.ts:10 — status is typed as plain string on the model and we cast to PhoneCallStatus externally in operations.ts:18. The cast hides the fact that status could be any string at runtime — if a future migration ever writes a new status value, downstream consumers silently get an unknown variant typed as PhoneCallStatus. Lets type the model field with the union directly so the cast is unnecessary and write-time typos get caught.